home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Software Vault: The Gold Collection
/
Software Vault - The Gold Collection (American Databankers) (1993).ISO
/
cdr11
/
intmemry.zip
/
MEMO1060.TXT
< prev
next >
Wrap
Text File
|
1992-12-02
|
21KB
|
454 lines
╔═════════════════════════════════════════════════════════════════════════╗
║ ║
║ ISA Bus: Symptoms/Solutions: Most Common Problems ║
║ ║
╚═════════════════════════════════════════════════════════════════════════╝
IBM TOKEN RING (& 16/4)
Compatible with Above Boards and EMM. If the Above Board will be providing
extended memory, there will be nothing to reconfigure with the Token Ring
Card. If the Above Board is providing expanded memory, the Token Ring and
the Above Board must be set up so they don't conflict with each other in
reserved memory.
To set up EMM and a Token Ring card:
1. Use the D000 parameter in the DEVICE=EMM.SYS line for AT's, E000
for PCs.
2. Set switches 1-6 on block #1 of the Token Ring Board to use CC000
(which is the default) as the ROM starting address. (pgs 2-3 of
Token Ring manual)
3. In AT systems it will be necessary to change the shared RAM
address using the TOKREUI command or DXMC0MOD.SYS (or
DXMC1MOD.SYS) driver (drivers for IBM LAN Support Program, ver
1.0.). In PC systems this step isn't necessary.
With newer lan software use the device driver:
Device=DXMC0MOD.SYS ,C800. With the original Token Ring software,
add the command TOKREUI ,C800 to the autoexec.bat file.
If there is a long number following the DXMC1MOD.SYS driver, don't
add the space before the comma. See the next scoop cell "...long
# after DXMC1MOD.SYS" for more details.
If they have Banyon LAN software, use PCCONFIG program to change the
Shared RAM address instead of Autoexec.bat.
Pages 4-7 in the Token Ring manual describe how to reset the "shared RAM"
address. There is also a very useful Memory Map listing on page B-2 in
this manual.
TOKEN RING & "LONG # AFTER DXMC1MOD.SYS"
If you see a long number following DXMC1MOD.SYS when editing the line to
add " ,C800" for Token Ring/EMM conflicts, don't add the space. The
DXMC1MOD.SYS driver will return the error mentioned above if there is a
space inbetween the long number and ",C800" or whatever address is used.
The 12 digit number following the DXMC1MOD.SYS driver is called the
"Locally Administered Address" (a hexidecimal address which overrides the
preprogrammed address of the board).
The "L.A.A." simplifies the process of adding workstations to the network
since all workstation addresses are preprogrammed into the host. A
workstation can then use just one preprogrammed address to be recognized
by the host.
The DMXC1MOD.SYS seems to be used when the computer will interface with a
"3270" type system. ("DXMC0" seems to be for PC only operation)
TOKEN RING & IPX
In Novell networks, it is possible to change the Shared RAM address of the
Token Ring board (which defaults at D800H) by modifying the IPX line in
the Autoexec.bat file.
The parameters are:
IPX O,PRI,MEM=xxxx
Where xxxx is the address you'd like to move the Shared RAM address to.
For instance, to move the Shared RAM address to C800H:
IPX O,PRI,MEM=C800
^this is the letter "o" as in Option, NOT the number 0 (zero).
TOKEN RING, EMM, AND 8088/8086 SYSTEMS
Since the E0000h range is not reserved for system use in 8088 and 8086
systems, try the EXPF=E000 parameter on the EMM.SYS line of the CONFIG.SYS
file. If the E0000h range is not being used by any other add-in boards, it
would be possible to move our driver out of the way of the Token Ring
drivers without having to rearrange the Token Ring drivers to make
everything fit.
OBTAIN THE MOST CURRENT ABOVE BOARD SOFTWARE
There are 2 methods of obtaining the most current Above Board software:
1. If you have a Modem you can use it to contact the Intel BBS or
CompuServe for the latest software.
2. If you do not have a modem you are located in the United States or
Canada, you can contact the Intel Order Department at (503) 222-
5393 and order the appropriate packet number:
Packet #25 5.25" installation diskette $15
Packet #27 3.5" installation diskette $15
For a complete listing of what's available from the Intel
Order Department you can request document 9012 from our
FaxBACK service. IMPORTANT NOTE: The Intel Order Department
can only ship items to locations within the United States and
Canada.
OBTAIN INSTALLATION INSTRUCTIONS
There are 3 methods of obtaining the Above Board installation
instructions:
1. If you have access to a Modem you can use it to contact the Intel
BBS or CompuServe for the latest software.
2. If you have access to a FAX machine you can use our "on-demand"
FAX service, FaxBACK.
For Above Board PC instructions......Document 1210
For Above Board PS/PC instructions...Document 1212
For Above Board AT instructions......Document 1214
For Above Board PS/AT instructions...Document 1216
For Above Board 286 instructions.....Document 1218
For Above Board Plus instructions....Document 1310
For Above Board Plus 8 instructions..Document 1312
3. If you do not have a modem and you are located within the United
States or Canada, you can contact the Intel Order Department at
(503) 222-5393 and order the appropriate packet number:
For Above Board PC instructions......Packet 33 ($15 charge)
For Above Board PS/PC instructions...Packet 34 ($15 charge)
For Above Board AT instructions......Packet 31 ($15 charge)
For Above Board PS/AT instructions...Packet 32 ($15 charge)
For Above Board 286 instructions.....Packet 35 ($15 charge)
For Above Board Plus & Plus 8........Packet 29 ($15 charge)
For a complete listing of what's available from the Intel
Order Department you can request document 9012 from FaxBACK.
IMPORTANT NOTE: The Intel Order Department can only ship
items to locations within the United States or Canada.
IDENTIFYING AN ABOVE BOARD BY SERIAL NUMBER
The serial number is located on a long white bar-code type label.
There are two serial number formats Intel has used over the years.
The older serial number format:
There are two sets of numbers on this label. The first set starts with two
letters and is the serial number. The second set of numbers on this label
usually starts with 30 and is just a production run number.
Shipped
Serial Product Memory Product
Code Code Config Name
--- --------- ------ --------
AA PCMB 1000 0K Above Board PC
AB PCMB 1010 64K Above Board PC
AC PCMB 1020 256K Above Board PC
AD PCMB 1025 2048K Above Board PC
AE PCMB 1025E 2048K Above Board PC Evaluation Unit
AG PCMB 1100 0K Above Board PS/PC
AH PCMB 1110 64K Above Board PS/PC
AJ PCMB 1120 256K Above Board PS/PC
AL PCMB 1125 1536K Above Board PS/PC
AM PCMB 1125E 1536K Above Board PS/PC Evaluation Unit
BA PCMB 2000 0K Above Board AT
BB PCMB 2010 128K Above Board AT
BC PCMB 2020 512K Above Board AT
BD PCMB 2025 2048K Above Board AT
BE PCPB 2000 0K Above Board AT Piggyback option
BG PCPB 2010 128K Above Board AT Piggyback option
BH PCPB 2020 512K Above Board AT Piggyback option
BJ PCPB 2025 2048K Above Board AT Piggyback option
BK PCMB 2025E 2048K Above Board AT Evaluation Unit
BM PCMB 2100 0K Above Board PS/AT
BN PCMB 2110 128K Above Board PS/AT
BQ PCMB 2120 512K Above Board PS/AT
BR PCMB 2125 1536K Above Board PS/AT
BS PCMB 2125E 1536K Above Board PS/AT Evaluation Unit
EB PCMB 4020 512K Above Board 286
EC PCMB 4025 2048K Above Board 286
EE PCMB 4120 512K Above Board PS/286
EG PCMB 4125 2048K Above Board PS/286
EK PCPB 4220 w/512K Above Board Piggyback option (2meg Max)
EL PCPB 4225 w/2Meg Above Board Piggyback option (2meg Max)
EP PCPB 4325 w/2Meg Above Board Piggyback option (6Meg max)
FA PCMB 2000 0K AB/AT
FB PCMB 2010 128K AB/AT
FC PCMB 2020 512K AB/AT
FD PCMB 2025 2048K AB/AT
HA PCMB 2000 0K AB/AT
HB PCMB 2010 128K AB/AT
HC PCMB 2020 512K AB/AT
HD PCMB 2025 2048K AB/AT
LB PCMB 4320 w/512K AB Plus
LC PCMB 4325 w/2Meg AB Plus
LE PCMB 4420 w/512K AB Plus I/O
LG PCMB 4425 w/2Meg AB Plus I/O
LL PCMB 4525 w/2Meg AB Plus 8
LQ PCMB 4625 w/2Meg AB Plus 8 I/O
MB PCMB 4320 w/512k AB Plus w/128k extended mem. addressing
MC PCMB 4325 w/2Meg AB Plus w/128k extended mem. addressing
ME PCMB 4420 w/512k AB Plus I/O w/128k ext. mem. addressing
MG PCMB 4425 w/2Meg AB Plus I/O w/128k ext. mem. addressing
MK PCMB 4700 w/0K Matched Memory Classic with No SIMMs
The newer serial number format:
Shipped
Serial Product Memory Product
Code Code Config Name
---------- --------- ------ --------
308125-xxx PCMB 4900 w/0K AB ISA with No SIMMs
308126-xxx PCMB 4920 w/2Meg AB ISA with two 1MB SIMMs
308127-xxx PCMB 4940 w/4Meg AB ISA with four 1MB SIMMs
CONFIGURING FOR EXTENDED MEMORY
Only 80286 CPUs or newer can address extended memory.
For Above Boards without switches run the SETBOARD program and choose the
Manual Installation Option. If the Above Board has switches, the switches
must be set for the correct extended memory beginning address and ending
address.
For both types of Above Boards it is critical to choose the correct
extended memory beginning address and ending address. Our boards go by the
actual memory addresses, so it is important to know the basics of the
computer's memory map.
0 - 640k Conventional or Base memory.
640k - 1024k Reserved address space for computer housekeeping.
1024k Extended memory start address.
If a computer only has 640k of memory, it is still using address space
between 640k - 1024k for the computer's BIOS (Basic Input and Output
Services) functions, and add-in card ROMs (Read Only Memory). This is why
extended memory starts at the 1024k address instead of the 640k address.
The Reserved Memory address space does NOT count when the computer is
testing conventional and extended memory.
From this we can see that if a computer counts up 1024k of total memory,
that 1024 is 640k of conventional memory from 0 - 640k, and 384k of
extended memory from 1024 - 1408k.
Configuration examples:
Example 1:
An Above Board with 2meg of memory to be used as extended memory
is being installed into a computer with only 640k of conventional
memory.
Starting address 1024k (since there's no other extended
in this system).
Ending address 3072k (if we start at the 1meg address
and continue out for 2meg, we
essentially come up with
1024 + 2048 = 3072).
Example 2:
An Above Board with 2meg of memory to be used as extended memory
is being installed into a computer with 1024k of memory.
Starting address 1408k (since there's already 384k of
extended memory on the system
board starting at 1024k, the
Above Board would start where
the system board would end, ie
1024 + 384 = 1408).
Ending address 3456k (if we start at the 1408 address
and continue out for 2meg, we
essentially come up with
1408 + 2048 = 3456).
NOTE: In some Intel 80386-based systems, there may be some of the
system board memory that is being used as Shadow RAM, or is
being used to cache the BIOS into physical memory. When this
happens the cache memory is using the address space between
640 and 1024k, so is not using the addresses it would
normally use.
Let's say there is 1024k on such a system, the 384k that would normally be
extended memory from 1024k to 1408k has essentially been transferred to
the 640-1024k range. In this case the Above Board would start at the 1024
address, since it is the first open address. In most cases you can
determine if any system extended memory is being used as cache or "Shadow"
memory by viewing the system setup diskette for that particular computer.
ABOVE BOARD MSG 40 "YOUR COMPUTER IS NOT COMPLETELY COMPATIBLE..."
Msg 40 "Your computer is not completely compatible with the IBM AT"
This error occurs if you are using an older version of the EMM.SYS
expanded memory manager with DOS 5.0.
This error can also occur if you are using an older version of the EMM.SYS
driver and are attempting to install the Above Board into a "compatible"
computer that contains a ROM BIOS different from the ROM BIOS of an IBM
AT.
To correct the error, update the EMM.SYS driver to version 4.0 rev D or
later, (diskette dated 6/90 or later). The latest Above Board software is
available 24 hours a day on the Intel BBS.
MEMORY NOT RECOGNIZED ON A COLD BOOT...ABOVE BOARD ISA
Above Board ISA extended memory, (and conventional memory backfill if
applicable), are not recognized on a cold boot.
This symptom can be caused by the combination of two things:
A marginal component on the Above Board ISA along with a "weaker" power
supply.
A small number of Above Board ISA's were built with a marginal Motorola
chip in position U3, (see below for location description). This chip
sometimes would not recognize a system reset signal on a cold boot if the
system power supply is not robust, meaning, this symptom will not happen
on all systems.
Above Board ISA's exhibiting this symptom should be replaced.
Always check for the Motorola chip in position U3. The chip will have the
code "LS14" and will have a small circle with an "M" inside it,
(Motorola). Position U3 is located just under the I/O Option connector
pins on the board. It is in between positions C6 on the left and C2 on
the right.
HWSETUP STUCK IN AN AUTOMATIC CONFIGURATION LOOP...ABOVE BOARD ISA
The HWSETUP configuration program for the Above Board ISA can get stuck in
an Automatic Configuration loop on certain systems.
Upgrade to HWSETUP v1.01 if you are experiencing this symptom. The latest
Above Board ISA Installation software is available on the Intel BBS.
The only known cause for the loop is having empty memory sockets on the
system board when adding an Above Board ISA. You should always fill the
system board memory sockets completely before adding an Intel Above Board.
The ONLY known workaround is when the system board has jumpers or switches
to set the system board memory size. In this case you can try setting the
system board memory size switches for the amount of memory on the system
board ONLY. This MAY allow an Above Board to function properly in the
system.
16BIT BOARDS AND ABOVE BOARDS
If the EMM.SYS locks up on the copyright notice, there's a very good
chance the EMM.SYS is running into a 16-bit reserved memory conflict.
If the Above Board Plus (or Plus 8) is set up for only extended memory, or
only conventional memory, or only conventional and extended memory there
will be no 16-bit conflicts with other 16-bit boards.
An Above Board Plus (or Plus 8) using Intel's EMM.SYS driver may run into
a conflict with other add-in boards that are doing a 16bit ROM access in
the C0000-DFFFFh range.
If the other add-in board is doing a true 16bit ROM access we can add the
parameter mentioned below to Intel's EMM.SYS line and there should be no
problems.
If the board is fluctuating between 16bit and 8bit (like almost all 16bit
VGA boards) the following parameter won't help, they'll have to put the
other board into either a true 16bit ROM mode or 8bit ROM mode.
The EMM.SYS parameter is 16BIT=xx, where xx is a value representing the
range that the other 16bit board(s) are using (excluding the EMM page
frames) based on the table listed below.
C000 = 01 Hex
C400 = 02 Hex
C800 = 04 Hex
CC00 = 08 Hex
D000 = 10 Hex
D400 = 20 Hex
D800 = 40 Hex
DC00 = 80 Hex
Examples:
To force 16bit accesses in C000 and D400 you would get:
01 Hex (C000)
+ 20 Hex (D400)
---------------
21 Hex, so you would use: 16BIT=21
To force 16bit accesses in the range C000 through CBFF
you would get:
01 Hex (C000)
+ 02 Hex (C400)
+ 04 Hex (C800)
---------------
07 Hex, so you would use: 16BIT=07
This gets fun when the numbers in a column add up to more
than 9, then you have to use A through F for 10 through 15.
For D800 and DC00 you would get:
40 Hex (D800)
+ 80 Hex (DC00)
---------------
C0 Hex, so you would use: 16BIT=C0
CHKMEM DOESN'T COUNT ALL OF THE EXTENDED MEMORY
Symptom: CHKMEM doesn't show the total amount of extended memory in the
system, or doesn't show any of the extended memory at all. This can be
caused by the way some DOS resident programs install themselves, could be
due to the OS/2 accesses extended memory, or due to an XMS (i.e.
HIMEM.SYS) driver being installed. The section below discusses these
possibilities in more detail.
When certain resident programs are installed, such as IBM's Cache, VDISK,
and PC-Kwik amoung others, the amount of uncounted memory will be the size
that the resident software has allocated.
The reason: CHKMEM asks the BIOS for the amount of conventional and
extended memory. Whatever the BIOS reports, it displays that without any
checking. Using IBM's cache as an example, it chains into INT 15 (which
knows about the amount of extended memory in the system), and re-adjusts
the amount of extended memory by the size of the cache. That way no other
software knows about the extended memory the cache software is using and
this insures nothing else will inadvertantly overwrite the cache (in this
example). There are several resident programs that handle extended memory
in exactly the same way.
In the "compatibility box" of OS-2, CHKMEM will report NO extended memory;
OS-2 claims all extended memory in a similiar fashion as do the DOS
resident programs listed above, and CHKMEM is reporting logical memory
available, not physical.
Another possibility is that an XMS (eXtended Memory Specification) driver
has been loaded. HIMEM.SYS is one example of an XMS Driver. XMS drivers
manage extended memory in such a way that if a program were to try to
access the extended memory without going through the XMS driver it would
tell the program there isn't any extended memory available at all.
CHKMEM looks solely for extended memory, and does not look for extended
memory through an XMS-type driver. This means that if an XMS driver is
present CHKMEM won't be able to find the extended memory that's under the
control of the XMS driver (which is ALL of the extended memory).
══════════════════════════════════════════════════════════════════════════════
End of file Intel FaxBack # 1060 December 2,1992